﻿<?xml version="1.0" encoding="utf-8"?>
<data>
  <Article ID="1" Code="Basics" Title="Basics of the Application interface" Description="The basic building block of the user interface is the 'Business Entity'. Every piece of application (e.g. User, Currency) acts as the Business Entity, which can be added, changed and also deleted. And as the essence there is powerful searching and listing interface, which supports even the exporting to the MS Excel (XML format)." IsVisible="true"
  CreationDate="2011-05-25T12:34:56.7" ReleaseDate="2010-08-25T12:34:56.7" LastUpdateDate="2010-08-25T12:34:56.7" ArticleCategoryId="2" ArticleGroupId="2">
    <Text>
|H2 [NAME:top] The Application basic User interface overview

|P Index
[NUM
[URL:#appName | TEXT:Application Name]
[URL:#logo    | TEXT:Logo]
[URL:#lang    | TEXT:Language and format selectors]
[URL:#quick   | TEXT:Quick Actions]
[URL:#bread   | TEXT:Bread-crumb control]
[URL:#page    | TEXT:Paging on the detail level]
[URL:#menu    | TEXT:Menu]
[URL:#action  | TEXT:Actions ]
[URL:#user    | TEXT:User information]
[URL:#button  | TEXT:Buttons (editing)]
[URL:#view    | TEXT:View selectors (page layout)]
NUM]

[IMG: files/basics/AppOverview.png | WIDTH: 686px; | HEIGHT: 553px; ]

|PR [URL:#top | TEXT: top]
|H3 [NAME:appName] I. Application Name

Application name (displayed in the upper left corner) describes the application. This text is also navigable and the click will redirect user to the Application home page.
Text of the Application name could be adjusted in the [SAMP:Translator] management, by setting the entity with the key [B:[I:ApplicationName ]](this also allows the different naming for different cultures)


|PR [URL:#top | TEXT: top]
|H3 [NAME:logo] II. Logo
Company Logo provides the second quick way how to get to the Home page. Click on the Logo image will navigate the same way as the Application Name.


|PR [URL:#top | TEXT: top]
|H3 [NAME:lang] III. Language and format selectors
Application is by default ready to operate in multi-language mode. Users can select their 'suitable' culture (by clicking the flag in the upper right corner).
(E.g. [IMG:i/en-GB.png| FLOAT:left;] for British formatting and English phrases)
Selected language has impact on Application behavior in two aspects:
[NUM
Localizing the phrases (description of buttons, actions etc.)
Date and Number formats
NUM]

|H5 Localization
The phrases localizing is in this application very simple, and can be maintained, changed and extended even in production environment.
[IMG:files/Basics/Localization.png | WIDTH: 117px; | HEIGHT: 60px; ]
In the Menu (the TreeView on the left) you can select the [SAMP:Localization] sub-items
[LI
Language
Translator
LI]
These two links will navigate user to the usual [SAMP:Business entities] management.

|H6 Language
Languages can be simply added or removed. This has an impact on the offered languages set int upper right corner.
When user selects the Language this way, Date and Number formats are adjusted to the selected culture standards.

Selected Language also decides about the used phrases on the screen. If there is for example localized phrase for the [DEF:New] (e.g. 'Neu' in German) then it is used. In other cases, the default (usually the English) is used.


|H6 Translator


Translator is (again) only the usual [SAMP:Business Entity], providing the simple way for adjusting the User Interface.
The next picture is an example of EDIT screen for the phrase of the 'New' Key-word.
[IMG:files/Basics/Translator.png | WIDTH: 689px; | HEIGHT: 353px; ]
For any combination (Key, Area) used in application could be the final phrase adjusted this way. The list of languages available in this editing screen depends on the 'allowed' languages (described above).



|PR [URL:#top | TEXT: top]
|H3 [NAME:quick] IV. Quick Actions

There are [VAR:Actions] available on every page. These are accessible by selecting the tab 'Actions' in the left column. These are described in the section below [URL:#action  | TEXT:Actions ].

The mostly used [VAR:Actions] have an abbreviated access in so called Quick actions menu:
[IMG:files/Basics/Quick.png | WIDTH: 229px; | HEIGHT: 62px; ]
The actions on the picture are (from the left):
[LI
New
filter
List view
Export to Excel
LI]

As the picture demonstrates, user can also execute these actions using the [VAR:shortcut key]. For instance there is the [DEF: Shift + Alt + E] to call 'export to excel' action.

|PR [URL:#top | TEXT: top]
|H3 [NAME:bread] V. Bread-crumb control
Bread crumb control is the information area. It provides the assembled description about current page.
[IMG:files/Basics/Breadcrumb.png | WIDTH: 408px; | HEIGHT: 37px; ]
For example (as shown on the picture) there are 4 parts describing the current page
[NUM
Application name - click on this hyperlink will navigate user to the home page
Business Entity (ore business area) - click on this will navigate to the default page of current Business area
Action name - currently executed action e.g. New, Edit, List ...
[I:Optional] is the Entity description (only on detail, or edit screens)
NUM]


|PR [URL:#top | TEXT: top]
|H3 [NAME:page] VI. Paging on the detail level
The [SAMP:Business Entities] are in this application basically managed in so called CRUD steps:
[LI
C - Create (New action)
R - Read (filter and List)
U - Update (Edit button)
D - Delete
LI]

During the R step, user can use searching which results in the List view. The detail view can be easily accessed from the list view by clicking the found rows. To provide more smooth way to iterate the details
and skipping these steps:
[LI
[I:go to one detail]
[I:back to list]
[I:go to another detail]
LI]

[IMG:files/Basics/Paging.png | WIDTH: 172px; | HEIGHT: 62px; ]
There are Paging (moving) buttons on the detail level. User therefore can directly navigate to the next or previous Entity. Of course, these actions are again accessible via [VAR:shortcut key]


|PR [URL:#top | TEXT: top]
|H3 [NAME:menu] VII. Menu (main TreeView navigation)
The central navigation point is situated in the left column - TreeView Menu:
[IMG:files/Basics/Menu.png | WIDTH: 186px; | HEIGHT: 332px; ]
Items of this tree are either (not navigable) Cluster Nodes (e.g. Business) which gathers similar [VAR:Items] or the links to the Default pages of every available [SAMP:Business Area] (Entity).

The offered menu items depend on the User access rights. For instance, if the user has the [DFN:Administrator] role, there is the Administration Cluster node. Without such right, the Menu does not display this item at all.

At any place of the application user can RIGHT click on the link (even in the TreeView menu) and select 'Open in the new Window or Tab'. This will enable to operate with different parts of the application in different windows. There is no limitation about this feature.
[I:Users are also allowed to click the [VAR:BACK] button of the browser to return to previously edited screen. This approach will have no impact to previously stored changes; it only allowes to go back and start new navigation from some of the previously seen page].


|PR [URL:#top | TEXT: top]
|H3 [NAME:action] VIII. Actions
Every [SAMP:Business Area] has the default view. For Entities it is usually the list view (unless the users during the development decided to change this behavior).
From that point user can interact whit the application using the proposed actions:
[IMG:files/Basics/Actions.png | WIDTH: 188px; | HEIGHT: 208px; ]
These are available (all of them) in the Left navigation column below the [VAR:Actions Tab].
The frequently used actions are also available in the [URL:#quick   | TEXT:Quick action icon list].


|PR [URL:#top | TEXT: top]
|H3 [NAME:user] IX. User information
User name and login (used for authorization) are displayed in the User information area:
[IMG:files/Basics/User.png | WIDTH: 192px; | HEIGHT: 95px; ]
Also the currently applied [URL:#lang    | TEXT:Language and Culture] (date and number formatting) are displayed. If application is using the [DFN:Current role approach] - User Information area also contains the link to the [VAR:Role selector] (Just test it).
The [DFN:Current role approach] has one essential advantage for users: They can act with application in different roles e.g.
[LI
[SAMP:Administrator]
[SAMP:Standard User]
LI]
Whenever there is need to execute [I:potentially dangerous] actions (change user rights, remove user) which could lead to the fatal impacts, user have to switch into the more powerful role: [SAMP:Administrator].
When this need is over (changes were made) user can again switch back to daily role [SAMP:Standard User]. This will decrease the potential danger to change unwanted settings in the day-to-day job.


|PR [URL:#top | TEXT: top]
|H3 [NAME:button] X. Buttons (editing)
Side by side with [VAR:Actions] there are the [VAR:Buttons]. Both have in fact very similar meaning: to react with the current [SAMP:Business Area] interface. In comparison with [VAR:Actions] (described above) the [VAR:Buttons] are more connected to the currently executing action:
[IMG:files/Basics/Buttons.png | WIDTH: 224px; | HEIGHT: 70px; ]
If user is editing some [SAMP:Business Entity] she/he can finally decide what to do (Save or Cancel).
Similar decisions exist on almost every page (filter or Clear parameters on the filter-screen etc.)
Some buttons also provides the [VAR:shortcut key]...


|PR [URL:#top | TEXT: top]
|H3 [NAME:view] XI. View selectors (page layout)
The common page layout could be not suitable for every situation. If user needs to print the detail, the areas around (Header, Navigation column ...) do not need to be seen.
For such situations there are 3 common Views available:
[IMG:files/Basics/View.png | WIDTH: 126px; | HEIGHT: 54px; ]
[LI
Default (with all that stuff around)
Detail (Useful for editing the large and complicated detail)
Print (no colors, no stuff around)
LI]

Suggested are always only two remaining views.
For every [SAMP:Business Entity] there could be made decision for the type of view on the [VAR:filter-screen].
[IMG:files/Basics/ListDetail.png]
This will affect the List-Detail navigation, if the current or some new window will be used to display the detail and in which view-type (Detail, Default, Print ...) it will be rendered [I:test it]

|PR [URL:#top | TEXT: top]
</Text>
  </Article>
  <Article ID="2" Code="Administration" Title="How to manage application" Description="Users and rights management, Roles in the application." IsVisible="true"
  CreationDate="2011-05-25T12:34:56.7" ReleaseDate="2010-08-25T12:34:56.7" LastUpdateDate="2010-08-25T12:34:56.7" ArticleCategoryId="2" ArticleGroupId="2">
    <Text>
|H2 [NAME:top] The Application administration

|P Index
[NUM
[URL:#current | TEXT:Current Role]
[URL:#admin   | TEXT:Administration]
[URL:#user    | TEXT:User]
NUM]


|PR [URL:#top | TEXT: top]
|H3 [NAME:current] I. Current Role

The [DFN:Current role approach] has one essential advantage for users: They can act with application in different roles e.g.
[LI
[SAMP:Administrator]
[SAMP:Standard User]
LI]
Whenever there is need to execute [I:potentially dangerous] actions (change user rights, remove user) which could lead to the fatal impacts, user have to switch into the more powerful role: [SAMP:Administrator].
When this need is over (changes were made) user can again switch back to daily role [SAMP:Standard User]. This will decrease the potential danger to change unwanted settings in the day-to-day job.

|H5 How to change [DFN:Current role]
Next picture in the left bottom corner provides the information about currently selected role ([SAMP:Administrator] in this case - mared 'I.')
[IMG:files/Administration/ChangeRole.png]

I.   Click on the currently selected role link (left bottom corner, e.g. Administrator - 'I.')
II.  Click on the button (marked with II.) to get the role list
III. Select intended role (e.g. Administrator for more powerful rights)
IV.  Save the newly selected role - click the [VAR:Select application role] button marked with 'IV.'

This approach is available for every user of the application. Only the list of accessible roles depends on the User settings (see [URL:#admin   | TEXT:Administration])

The Menu items now should be different. Each role has different rights and therefore different Menu-items.


|PR [URL:#top | TEXT: top]
|H3 [NAME:admin] II. Administration (menu item)

Administration contains the User management and optionally Application specific settings. This management is available in the Menu Item called [VAR:Administration] (marked with 'I.' on the picture below)

[IMG: files/Administration/AdminSelection.png ]

If there is NOT [VAR:Administration] menu item displayed, then User must switch to the [SAMP:Administrator] role (if there is such an option for this User). (See [URL:#current | TEXT:Current Role])

When successfully switched to the [DFN:Current role] -&gt; [SAMP:Administrator], there will be the Menu Item 'Administration' available with User management as displayed on the next picture
[IMG:files/Administration/UserManage.png]

How to Manage user (add, change the rights) is described in the section [URL:#user    | TEXT:User].

|PR [URL:#top | TEXT: top]
|H3 [NAME:user] II. User

User is a standard Business Entity (in the manner of its management). Users can be added, changed and removed. To enter the User management select the User menu item in the Administration node (see the picture below). The default (enter) screen for User management is the list - overview of all already existing users.
[IMG:files/Administration/UserList.png]

To add new User to the Application, click the quick Icon [IMG:i/quick/new.png] or use the [VAR:shortcut key] Shift + Alt + N. The editing screen will appear:
[IMG:files/Administration/UserNew.png]

Every User-Entity is unique by its Login property (Another entity could have unique Code etc.).
For purposes of this application it is the Windows authenticated [VAR:Login] without the domain (e.g. wrong [BLUE:[S:PCNAME\UserLogin]], right [PURPLE:[U:UserLogin]])

Finally click the Add button or use the [VAR:shortcut key] Shift + Alt + S. This will store the newly created User record with the rights - in our case [SAMP:Viewer]. The 'Viewer' role will allow user to see some parts of application - always in the READONLY mode.

The list of Users will now display two records (the new row marked with 'II.'). Also Observe the headers which allow to sort, simply click.
[IMG:files/Administration/UserList2.png]
Every list view also provides the direct Excel exporting. You can either click the Excel sheet icon  [IMG:i/quick/listToExcel.png] or use the [VAR:shortcut key] Shift + Alt + E.

Click on the row will navigate to the 'detail' view or to the 'edit' view (the 'Edit' column in the list view). Then selected enity can be changed, in the same way as it was newly added.


This entity management is very simple. There are no hidden but. Similar behavior is applied on any other [DFN:Business entity] management in the application.

|PR [URL:#top | TEXT: top]
</Text>
  </Article>
  <Article ID="3" CreationDate="2011-05-25T12:34:56.7" LastUpdateDate="2011-05-26T07:13:32.8192021+02:00" ReleaseDate="2010-08-25T12:34:56.7" IsVisible="true" ShowComment="false" Code="Wiki" Title="Wiki .NET Syntax" Description="Description of the Wiki .NET Syntax. How to write headers, text, hyper-links, append images and zipped files and many more. Every element is described and provided with sample code. &#xD;&#xA;The major intention of the Wiki .NET Syntax was to provide as easy way to describe text as possible. Once this target is fit, then Wiki .NET Parser can be used in a day to day practice." ArticleCategoryId="2" ArticleGroupId="2">
    <Text>|H1 WIKI.NET [NAME:top]

[NUM
[URL:#simpleText|TEXT: Simple Text]
[URL:#paragraph|TEXT: Headers and Paragraphs]
[URL:#lists|TEXT: Lists] [GREEN:[I:(extended)]]
[URL:#navigation|TEXT: Navigation]  [GREEN:[I:(fixed for long url)]]
[URL:#image|TEXT: Image]
[URL:#decoration|TEXT: Decorations and Colors]  [GREEN:[I:(extended)]]
[URL:#block|TEXT: Block]
[URL:#escaped|TEXT: Escaped character syntax]
[URL:#tables|TEXT: Tables]  [GREEN:[I:(new)]]
NUM]


|H2 Notes
|P1 This document is written in the [B:[GREEN:Wiki .NET]] Syntax and converted with the [B:[GREEN:Wiki .NET Parser]]  (and therefore could be taken as a proof of concept).
|P1 [B:[GREEN:WIKI.NET]] is based on the ANTLR3 for C#.NET. Very few rows of the lexer, grammar and AST Parser; future extensibility; easy maintainability; exceptional performance
|P1 Syntax of the [B:[GREEN:Wiki .NET]] is (from the highlighting point of view) mostly C# and XML oriented.
|P1 In next paragraphs there is complete description of the syntax with examples. Syntax elements could be split into these categories:

[LI
Blocks (special formatting like XML)
Inline Blocks (text)
Decoration (styles, colors)
Hyperlinks and images
LI]

|P1 As in another languages there is a small set of the special leading characters used in [B:[GREEN:Wiki .NET]] Syntax:
[LI
[SAMP:[PURPLE:[[]]] (opening block)
[SAMP:[PURPLE:[]]]] (closing block)
[SAMP:[PURPLE:[|]]] (inline block; attribute separator)
[SAMP:[PURPLE:[:]]] (attribute value starts)
LI]
|P1 These signs combined with keywords provides complete [B:[GREEN:Wiki .NET]] playground for safe text publishing.




|H2 [NAME:simpleText] Simple Text
|PR [URL:#top | TEXT: top]



|H3 Keywords
[LI
[SAMP:[I:(there are NO keywords)]]
LI]

|H3 Description
|P1 You can type text as it goes. It will be rendered as usual text without any formatting.

|P1 The newlines (ENTER) will be rendered as a html specific new lines (instead of "\r\n" - "&lt;br /&gt;").

|P1 More Spaces (more then 1) will be all rendered (not skipped). [I: (Standard HTML browser will convert multi-space into single one)]

|P1 Empty lines are skipped. To append empty line to the output, place the White space on the line [I:(white space and press ENTER)]

|H3 Syntax
[CODE
There is no special syntax, just type...

CODE]

|H3 Example

|H4 wiki
[CODE
1) Text with the
broken lines
2) Text with    spaces
CODE]

|H4 result
[BQ
1) Text with the
broken lines
2) Text with    spaces
BQ]










|H2 [NAME:paragraph] Headers and Paragraph
|PR [URL:#top | TEXT: top]




|P Headers and Paragraphs has the syntax based on 3 parts
[NUM
[SAMP:[BLUE:[|]]] Leading vertical line at the beginning
[SAMP:[BLUE:H1]] The name of the used header or paragraph
[SAMP:[BLUE:' ']] One WHITE SPACE!
NUM]
|H3 Keywords
[LI
[SAMP:[PURPLE:[|]H1 .. [|]H6 ]  ](headers)
[SAMP:[PURPLE:[|]P ]          ](paragraph)
[SAMP:[PURPLE:[|]P1 .. [|]P3 ]  ](paragraphs with different margins)
[SAMP:[PURPLE:[|]PC ]         ](center aligned paragraph)
[SAMP:[PURPLE:[|]PR ]         ](right aligned paragraph)
[SAMP:[PURPLE:[|]CITE ]       ](cite text (italic))
[SAMP:[PURPLE:[|]BQ ]         ](blockquote text with larger padding)
LI]

|H3 Description

|P1 Headers and Paragraphs allows formatting based on 'inline block' style.

|P1 It means, that the text between the opening symbol (e.g. '[SAMP:[PURPLE:[|]P ]]' and the end of line [I:(ENTER)] is rendered as a paragraph &lt;p&gt;...&lt;/p&gt;)


|H3 Syntax
[CODE
[PURPLE:[|]H1 ] Header 1
- &gt; &lt;h6&gt;Header 1 &lt;/h6&gt;
..
[PURPLE:[|]H6 ] Header 6
- &gt; &lt;h6&gt;Header 6&lt;/h6&gt;

[PURPLE:[|]P ] Usuall text...
- &gt; &lt;p&gt;Usuall text...&lt;/p&gt;

CODE]

|H3 Example

|H4 wiki
[CODE
[PURPLE:[|]H3 ] Lorem ipsum
[PURPLE:[|]P1 ] Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed dor eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

[PURPLE:[|]P2 ] Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum


[PURPLE:[|]CITE ] Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.

[PURPLE:[|]BQ ] Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt.

[PURPLE:[|]PR ] Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem.

CODE]

|H4 result
[BQ

|H3 Lorem ipsum
|P1 Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed dor eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

|P2 Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum

|CITE Sed ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.

|BQ Nemo enim ipsam voluptatem quia voluptas sit aspernatur aut odit aut fugit, sed quia consequuntur magni dolores eos qui ratione voluptatem sequi nesciunt.

|PR Neque porro quisquam est, qui dolorem ipsum quia dolor sit amet, consectetur, adipisci velit, sed quia non numquam eius modi tempora incidunt ut labore et dolore magnam aliquam quaerat voluptatem.

BQ]






|H2 [NAME:lists] Lists
|PR [URL:#top | TEXT: top]


|P1 There are two types of lists. Wrapped and inline, for both 'numbered' and 'pointed' types.

|H3 Keywords
Block syntax, uses starting and closing tags LI or/and NUM to wrap selected rows as list items.
[LI
[SAMP:'[[]LI'   'LI[]]'  ]
[SAMP:'[[]NUM'  'NUM[]]'  ]
LI]

Inline syntax will render every row as a list item if starting with one of below statements (the space sign after asterix or hash is important)
[LI
[SAMP:'* ']
[SAMP:'** ']
[SAMP:'*** ']
[SAMP:'# ']
[SAMP:'## ']
[SAMP:'### ']
LI]

|H3 Description
|P1 You can choose block or inline style. Block lists can be nested. Inline syntax must be correctly growing (cannot start with '** ')


|H3 Block Syntax
[CODE
[PURPLE:[[]LI ]
meals
colors
[PURPLE:[[]NUM ]
blue
red
[PURPLE: NUM[]]]
[PURPLE: LI[]]]
CODE]

|H3 Inline Syntax
[CODE
[PURPLE:* ] meals
[PURPLE:* ] colors
[PURPLE:## ] blue
[PURPLE:## ] read
CODE]

|H3 Result for both
[CODE
&lt;ul&gt;
&lt;li&gt;meals&lt;/li&gt;
&lt;li&gt;colors
&lt;ol&gt;
 &lt;li&gt;blue&lt;/li&gt;
 &lt;li&gt;red&lt;/li&gt;
&lt;/ol&gt;&lt;/li&gt;
&lt;ul&gt;
CODE]


|H3 Example

|H4 wiki
[CODE
 // blocks
[PURPLE:[[]LI ]
Meals:
Supported colors are:
[PURPLE:[[]NUM ]
blue
red
green
[PURPLE:NUM[]]]
[PURPLE: LI[]]]
 // inlines
[*] Meals:
[*] Supported colors are:
[#]# blue
[#]# red
[#]# green
CODE]

|H4 result
[BQ
 // blocks
[LI Meals:
Supported colors are:
[NUM blue
red
green NUM]
LI]
 // inlines
* Meals:
* Supported colors are:
## blue
## red
## green

BQ]










|H2 [NAME:navigation] Navigation
|PR [URL:#top | TEXT: top]





|H3 Keywords
[LI
[SAMP:[PURPLE:URL]]
[SAMP:[PURPLE:URL [|] TEXT]]
[SAMP:[PURPLE:NAME]]
LI]
|H3 Description

|P1 There are two keywords: [SAMP:URL] and [SAMP:NAME] for creating the hyperlinks.

|P1 The first [I:([SAMP:URL])] will result in the hyperlink with the [V:href] attribute (where to navigate). There are few different ways how to change the text of the hyperlink, if the [VAR:url] itself is not suitable (e.g. [DFN:&lt;a href="target"&gt;target&lt;/a&gt;] to [DFN:&lt;a href="target"&gt;my TEXT&lt;/a&gt;])

|P1 The second will create the anchor  [I:([SAMP:NAME])] to which could be page scrolled [I:(e.g. the 'top' hyperlinks navigating to the top of the page)]

|H3 Syntax URL
[CODE

[PURPLE:[[]URL:index.htm#top]] // only url
==&gt; &lt;a ref="index.htm#top"&gt;index.htm#top&lt;/a&gt;

[PURPLE:[[]URL: click here [|] index.htm#top]]          // short text first
==&gt; &lt;a ref="index.htm#top" &gt;click here&lt;/a&gt; // then vline '|' and url


// OR
[PURPLE:[[]URL:  index.htm#top [|]TEXT: click here]]    // first url
==&gt; &lt;a ref="index.htm#top" &gt;click here&lt;/a&gt; // then attr '|TEXT:' and text

[PURPLE:[[]URL: ["]index.htm#top["] [|]TEXT: click here]]   // quoted url (if too long and complicated url)
==&gt; &lt;a ref="index.htm#top" &gt;click here&lt;/a&gt; // |TEXT: next with an attr 'TEXT:'


CODE]

|H3 Syntax NAME
[CODE
[PURPLE:[[]NAME:top]]
- &lt;a name="top"&gt;&lt;/a&gt;
CODE]

|H3 Example

|H4 Wiki
[CODE
[PURPLE:[[]URL:#top]]   - only url
[PURPLE:[[]URL:TOP [|] #top]]  - text first


[PURPLE:[[]URL: #top  [|]TEXT: TOP]] - TEXT: attribute
[PURPLE:[[]URL:["]#top["] [|]TEXT: TOP]] - quoted url

CODE]
|H4 Result

[BQ
[URL:#top]  - only url
[URL:TOP|#top] - short text first


[URL:#top|TEXT:TOP]  - TEXT: attribute
[URL:"#top"|TEXT:TOP]  - quoted url
BQ]








|H2 [NAME:image] Image
|PR [URL:#top | TEXT: top]





|H3 Keywords
[LI
[SAMP:[PURPLE:IMG]]
[SAMP:[PURPLE:HEIGHT]]
[SAMP:[PURPLE:WIDTH]]
[SAMP:[PURPLE:FLOAT]]
LI]

|H3 Description
|P1 [SAMP:[PURPLE:IMG]] element allows you to insert the image into to the page.

|P1 The URL for image should be relative, for instance 'i/cs.png'

|P1 There is an issue with the virtual directories for applications. E.g. instead of [I:http://mydomain/] there is [I:http://mydomain/myvirtualdir/]. In these situations there is a background call which will change the IMG src attribute from  [S:[RED:'i/cs.png']] to  [GREEN:'myvirtualdir/i/cs.png'] and the image will be correctly displayed.

|H3 Syntax
[CODE
[PURPLE:[[]IMG:i/cs.png[]]]
==&gt; &lt;img src="i/cs.png" /&gt;

[PURPLE:[[]IMG:i/cs.png [|]HEIGHT:100px[|]WIDTH:80px[]]]
==&gt; &lt;img src="i/cs.png" style="height:100px;width:80px;" /&gt;

[PURPLE:[[]IMG:i/cs.png [|]FLOAT:right[]]]
==&gt; &lt;img src="i/cs.png" style="float:right;" /&gt;

CODE]

|H3 Example

|H4 wiki
[CODE

[PURPLE:[|]P1 ] Lorem ipsum dolor [PURPLE:[[]IMG:i/cs.png[]]]  sit amet, consectetur adipisicing elit, sed dor eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.

[PURPLE:[|]P2 ] Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. [PURPLE:[[]IMG:i/cs.png[|]HEIGHT:100px[|] WIDTH:80px[]]]  Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum

[PURPLE:[|]P3 ] Sed [PURPLE:[[]IMG:i/cs.png[|]FLOAT:right[]]]  ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.


CODE]

|H4 result
[BQ

|P1 Lorem ipsum dolor [IMG:i/cs.png]  sit amet, consectetur adipisicing elit, sed dor eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.


|P2 Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. [IMG:i/cs.png |HEIGHT:100px| WIDTH:80px]  Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum

|P3 Sed [IMG:i/cs.png|FLOAT:right] ut perspiciatis unde omnis iste natus error sit voluptatem accusantium doloremque laudantium, totam rem aperiam, eaque ipsa quae ab illo inventore veritatis et quasi architecto beatae vitae dicta sunt explicabo.

BQ]







|H2 [NAME:decoration] Decorations and Colors
|PR [URL:#top | TEXT: top]




|H3 Keywords
[B: Special bold and italic:]
[LI
[SAMP: [*]bold text[*]   ]*bold text*
[SAMP: [_]italic text[_] ] _italic text_
LI]

[B: Decorations:]
[LI
[SAMP:[PURPLE:B]     ][B:bold]
[SAMP:[PURPLE:I]     ][I:italic]
[SAMP:[PURPLE:U]     ][U:underline]
[SAMP:[PURPLE:S]     ][S:striked]
[SAMP:[PURPLE:V]     ][V:variable]
[SAMP:[PURPLE:SAMP]  ][SAMP:sample]
[SAMP:[PURPLE:BIG]   ][BIG:big]
[SAMP:[PURPLE:SMALL] ][SMALL:small]
[SAMP:[PURPLE:SUP]   ]sup [SUP:*sup]
[SAMP:[PURPLE:SUB]   ]sub [SUB:*sub]
LI]

[B: Colors:]
[LI
[SAMP:[PURPLE:BLUE]   ][BLUE:blue]
[SAMP:[PURPLE:RED]    ][RED:red]
[SAMP:[PURPLE:GREEN]  ][GREEN:green]
[SAMP:[PURPLE:OLIVE]  ][OLIVE:olive]
[SAMP:[PURPLE:LIME]   ][LIME:lime]
[SAMP:[PURPLE:PURPLE] ][PURPLE:purple]
[SAMP:[PURPLE:YELLOW] ][YELLOW:yellow]
[SAMP:[PURPLE:MAROON] ][MAROON:maroon]
[SAMP:[PURPLE:SILVER] ][SILVER:silver]
[SAMP:[PURPLE:ORANGE] ][ORANGE:orange]
[SAMP:[PURPLE:NAVY]   ][NAVY:navy]
[SAMP:[PURPLE:PINK]   ][PINK:pink]
LI]

|H3 Description
|P1 Decoration styles and colors are 'inline' elements. This means that these elements cannot contain new lines!

|P1 You can use them almost anywhere and if needed they can be even nested (e.g. bold and blue)

|H3 Syntax
[CODE
// bold and italic inside some row
.. not bold [*]now bold until here[*] not bold ..
==&gt; .. not bold &lt;b&gt;now bold until here&lt;/b&gt; not bold ..

.. not italic [_]now italic until here[_] not italic ..
==&gt; .. not italic &lt;i&gt;now italic until here&lt;/i&gt; not italic ..

// bold and italic
[PURPLE:[[]B:bold[]]]
==&gt; &lt;b&gt;bold&lt;/b&gt;

[PURPLE:[[]I:italic[]]]
==&gt; &lt;i&gt;italic&lt;/i&gt;


// COLOR example: blue and purple
[PURPLE:[[]BLUE:blue[]]]
- &gt; &lt;span style="color:blue;"
&gt;blue&lt;/span&gt;
[PURPLE:[[]PURPLE:purple[]]]
- &gt; &lt;span style="color:purple;"
&gt;purple&lt;/span&gt;

CODE]

|H3 Example

|H4 wiki
[CODE
[PURPLE:[|]CITE] This text could be partially [PURPLE:[[]B:]bold end even [PURPLE:[[]ORANGE:]orange[PURPLE:[]][]]]. And that all inside the big [PURPLE:[[]BIG:]CITE[PURPLE:[]]] element.
CODE]

|H4 result
[BQ
|CITE This text could be partially [B:bold end even [ORANGE:orange]]. And that all inside the [BIG:CITE] element.
BQ]






|H2 [NAME:block] Block
|PR [URL:#top | TEXT: top]



|P1 There are 3 special block elements for specific text rendering: CODE, XML, HTML. There is also the BlockQuote element: BQ.

|H3 Keywords
[LI
[SAMP:[PURPLE:CODE ]  ][I:C# syntax support]
[SAMP:[PURPLE:XML ]   ][I:xml syntax support]
[SAMP:[PURPLE:HTML ]  ][I:html specific syntax support]
[SAMP:[PURPLE:BQ ]    ][I:support for multi-line blockquote]
[SAMP:[PURPLE:PRE ]   ][I:renders PRE element]
LI]

|H3 Description

|P1 These block elementshas the special syntax which has OPENING and CLOSING tags. The text placed between the CODE, XML, HTML marks is rendered with special syntax support.

|P1 Usage of these element is extremely simple: just copy your code, and place it between [PURPLE:[[]CODE CODE[]]] elements. That's all


|H3 Syntax
[CODE
[PURPLE:[[]CODE ]
public interface IModel {}
[PURPLE:CODE[]]]
- &gt; &lt;code&gt;
&lt;span class="base" &gt;public&lt;/span&gt;
&lt;span class="base" &gt;interface&lt;/span&gt;
IModel&lt;br /&gt;
&lt;span class="smbl" &gt;{&lt;/span&gt;&lt;br /&gt;

&lt;span class="cmmnt"
&gt;// TODO&lt;/span&gt;&lt;br /&gt;
&lt;span class="smbl" &gt;}&lt;/span&gt;&lt;br /&gt;
&lt;/code&gt;

CODE]

|H3 Example

|H4 wiki
[CODE

[PURPLE:[|]H5 ] CODE

[PURPLE:[[]CODE ]
public interface IModel
{
// TODO
}
[PURPLE:CODE[]]]


[PURPLE:[|]H5] XML

[PURPLE:[[]XML ]
&lt;project&gt;
  &lt;settings&gt;
    &lt;mode value="Leveled"
       type="Fluent" /&gt;
    &lt;readability name="Inner" &gt;
      &lt;!-- TODO --&gt;
      ... extended in the next phase ...
    &lt;/readability&gt;
  &lt;/settings&gt;
&lt;/project&gt;
[PURPLE:XML[]] ]


[PURPLE:[|]H5] HTML

[PURPLE:[[]HTML ]
&lt;html xmlns="http://www.w3.org/1999/xhtml" &gt;
  &lt;head&gt;
    &lt;title&gt;&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;a href="Index.htm" &gt;
      Default&lt;/a&gt;
  &lt;/body&gt;
&lt;/html&gt;
[PURPLE:HTML[]] ]

CODE]



|H4 result
[BQ

|H5 CODE

[CODE
public interface IModel
{
   // TODO
}
CODE]


|H5 XML
[XML
&lt;project&gt;
  &lt;settings&gt;
    &lt;mode value="Leveled"
        type="Fluent" /&gt;
    &lt;readability name="Inner" &gt;
        &lt;!-- TODO --&gt;
        extended in the next phase
    &lt;/readability&gt;
  &lt;/settings&gt;
&lt;/project&gt;
XML]


|H5  HTML

[HTML
&lt;html xmlns="http://www.w3.org/1999/xhtml" &gt;
  &lt;head&gt;
    &lt;title&gt;&lt;/title&gt;
  &lt;/head&gt;
  &lt;body&gt;
    &lt;a href="Index.htm" &gt;
    Default&lt;/a&gt;
  &lt;/body&gt;
&lt;/html&gt;
HTML]


BQ]



|H2 [NAME:escaped] Escaped character syntax
|PR [URL:#top | TEXT: top]


|P1 There are some special characters used for this wiki markup. They are [B:leading symbols] and therefore cannot be used directly in the text

|P1 If they are used directly (without escaping) they could result in unwanted streams; or even break the whole page.

|H3 Keywords
[LI
[SAMP:[PURPLE:[[] ]]
[SAMP:[PURPLE:[]] ]]
[SAMP:[PURPLE:[|] ]]
[SAMP:[PURPLE:[:] ]]
[SAMP:[PURPLE:[&lt;] ]]
[SAMP:[PURPLE:[&gt;] ]]
[SAMP:[PURPLE:[*] ]]
[SAMP:[PURPLE:[#] ]]
[SAMP:[PURPLE:[_] ]]
[SAMP:[PURPLE:["] ]]
LI]

|H3 Description
|P1 To correctly render these signs you have to use the [B:escape syntax]

|P1 The syntax is simple: encapsulate the sign in these braces '[[]' '[]]'

|H3 Syntax
[CODE
[PURPLE:[[][[][]]]
==&gt; [[]
[PURPLE:[[][]][]]]
==&gt; []]
[PURPLE:[[][:][]]]
==&gt; [:]
[PURPLE:[[][|][]]]
==&gt; [|]
[PURPLE:[[][&lt;][]]]
==&gt; [&lt;]
[PURPLE:[[][&gt;][]]]
==&gt; [&gt;]
[PURPLE:[[][*][]]]
==&gt; [*]
[PURPLE:[[][#][]]]
==&gt; [#]
[PURPLE:[[][_][]]]
==&gt; [_]
[PURPLE:[[]["][]]]
==&gt; ["]

CODE]

|H3 Example

|H4 wiki
[CODE

[PURPLE:Index[[][[][]]2[[][]][]]]

to not display less and greater as the element
[PURPLE:[[]XML ]
[RED:&lt;wrong&gt;]
[PURPLE:[[][&lt;][]]right[[][&gt;][]]]
[PURPLE:XML[]]]

CODE]

|H4 result
[BQ
Index[[]2[]]
[XML
&lt;wrong&gt;
[&lt;]right[&gt;]
XML]
BQ]



|H2 [NAME:tables] Tables
|PR [URL:#top | TEXT: top]

|P1 Tables has been introduced following the usual syntax of the VLINE  [SAMP:[|]]
|P1 Use two VLINEs [SAMP:[|][|]] for a table head, and single VLINE [SAMP:[|]] for a table row

|H3 Keywords
[LI
[|]|
[|]
LI]
|H3 Syntax
[CODE
[|]| heading1 || heading2 // two VLINEs will render THEAD
[|]| heading3 || heading4
[|]  cell1    |  cell2    // single VLINE for a row
[|]  cell3    |  cell4
CODE]

|H3 Example

|H4 wiki
[CODE
[|]| id  || date     || name
[|]  123 |  1.2.2011 | myName
CODE]


|H4 result

|| id || date || name
|  123 |  1.2.2011 | myName


|PR [URL:#top | TEXT: top]

Enjoy the Wiki .NET Parser</Text>
  </Article>
  <Article ID="4" Code="Home" Title="Home" Description="Home"
  CreationDate="2011-05-25T12:34:56.7" LastUpdateDate="2010-08-25T12:34:56.7" ReleaseDate="2010-08-25T12:34:56.7" IsVisible="false" ShowComment="true" ArticleCategoryId="1" ArticleGroupId="1">
    <Text>Welcome aboard</Text>
  </Article>
</data>